Health Cloud Clinical System API - Implementation Template

(0 reviews)

Field mapping

Condition

FHIR Field NameSalesforce ObjectSalesforce Field NameNotes
Identifier.useIdentifierIdUsageTypeThe identifier information for a health condition is represented as Identifier records that reference the health condition record using their Identifier​.Parent​RecordId field.
Identifier.systemIdentifierSourceSystem
Identifier.valueIdentifierIdValue
Identifier.type.coding.codeIdentifierIDTypeId
clinicalStatus.coding.codeHealth​ConditionConditionStatusWhile FHIR defines Condition​.clinical​Status as a code set bundle, the Salesforce implementation of Health​Condition​.Condition​Status is picklist.
verificationStatus.codeing.codeHealth​ConditionDiagnosticStatusWhile FHIR defines condition​.verification​Status as a code set bundle, the Salesforce implementation of Health​Condition​.Diagnostic​Status is picklist.
category.coding.codeHealth​ConditionTypeWhile FHIR defines Condition​.category as a zero-to-many code set bundle, the Salesforce implementation of Health​Condition​.Categories is a zero-to-one picklist.
severity.coding.codeHealth​ConditionSeverityWhile FHIR defines condition​.severity as a code set bundle, the Salesforce implementation of Health​Condition​.Severity is picklist.
code.coding.codeHealth​ConditionConditionCodeIdWhile FHIR defines condition​.code as a zero-to-one resource, the Salesforce implementation is a one-to-one field.
bodySite.coding.codeHealth​ConditionSiteIdUse this field if only one bodySite value is required for the condition.
subject.referenceHealth​ConditionPatientIdThe Salesforce implementation of Condition​.subject doesn’t support groups.
encounter.referenceHealth​ConditionClinicalEncounterId
onsetA choice of more than one data types.
onset.onsetDateTimeHealth​ConditionOnsetStartDateTime
abatementA choice of more than one data types.
abatement.abatementDateTimeHealth​ConditionAbatementStartDateTimeHealth​Condition​.Abatement​Start​Date​Time is used as both the equivalent of condition​.abatement​.abatement​Date​Time and the start date of condition​.abatement​.abatement​Period
recordedDateHealth​ConditionRecordCreationDateTime
recorder.referenceHealth​ConditionRecordCreatorId
asserter.referenceHealth​ConditionAssertionSourceId
stage.summary.coding.codeHealth​ConditionStageIdThe child resources of condition​.stage is combined into a single code set bundle reference field. While FHIR defines condition​.stage as a zero-to-many resource, the Salesforce implementation is a zero-to-one field.

AllergyIntolerance

FHIR Field NameSalesforce ObjectSalesforce Field NameNotes
Identifier.useIdentifierIdUsageTypeThe identifier information for a health condition is represented as Identifier records that reference the health condition record using their Identifier.ParentRecordId field.
Identifier.systemIdentifierSourceSystem
Identifier.valueIdentifierIdValue
Identifier.type.coding.codeIdentifierIDTypeId
clinicalStatus.coding.systemAllergyIntoleranceWhile FHIR defines allergyIntolerance.clinicalStatus as a code set bundle, the Salesforce implementation of AllergyIntolerance.Status is picklist.
verificationStatus.coding.codeAllergyIntoleranceVerificationStatusWhile FHIR defines allergyIntolerance.verificationStatus as a code set bundle, the Salesforce implementation of AllergyIntolerance.VerificationStatus is picklist.
typeAllergyIntoleranceTypeWhile FHIR defines allergyIntolerance.category as a code set bundle, the Salesforce implementation of AllergyIntolerance.Categories is a picklist.
categoryAllergyIntoleranceCategoryWhile FHIR defines allergyIntolerance.category as a code set bundle, the Salesforce implementation of AllergyIntolerance.Category is a picklist.
criticalityAllergyIntoleranceSeverityWhile FHIR defines allergyIntolerance.criticality as a code set bundle, the Salesforce implementation of AllergyIntolerance.Severity is picklist.
code.coding.codeAllergyIntoleranceCodeId
patient.referenceAllergyIntolerancePatientId
encounter.referenceAllergyIntoleranceClinicalEncounterId
onset.A choice of more than one data types.
onset.onsetDateTimeAllergyIntoleranceOnsetStartDateTimeAllergyIntolerance.OnsetStartDateTime is used as both the equivalent of allergyIntolerance.onset.onsetDateTime and the start date of allergyIntolerance.onset.onsetPeriod
recordedDateAllergyIntoleranceRecordCreationDateTime
recorder.referenceAllergyIntoleranceRecordCreatorId
asserter.referenceAllergyIntoleranceAssertionSourceId
lastOccurrenceAllergyIntoleranceLastOccurenceDateTime
reactionPatientHealthReactionThe reaction information for an allergy intolerance is represented as PatientHealthReaction records that reference the AllergyIntolerance record using their PatientHealthReaction.ParentId field.
reaction.substancePatientHealthReaction
reaction.substance.coding.codePatientHealthReactionCausativeSubstanceId
reaction.manifestation.coding.codePatientHealthReactionManifestedSymptomIdWhile FHIR defines allergyIntolerance.reaction.manifestation as a one-to-many resource, the Salesforce implementation of PatientHealthReaction.ManifestedSymptomId is zero-to-one.
reaction.descriptionPatientHealthReactionDetails
reaction.onset.onsetDateTimePatientHealthReactionReactionDateTime
reaction.severityPatientHealthReactionSeverityWhile FHIR defines allergyIntolerance.reaction.severity as a code set bundle, the Salesforce implementation of PatientHealthReaction.Severity is a picklist.
reaction.exposureRoute.coding.codePatientHealthReactionExposureRouteId

Procedure

FHIR Field NameSalesforce ObjectSalesforce Field NameNotes
Identifier.useIdentifierIdUsageTypeThe identifier information for a Procedure is represented as Identifier records that reference the PatientMedicalProcedure record using their Identifier.ParentRecordId field.
Identifier.systemIdentifierSourceSystem
Identifier.valueIdentifierIdValue
Identifier.type.coding.codeIdentifierIDTypeId
basedOn.referencePatientMedicalProcedureDetailDetailRecordIdFor procedure.basedOn information, PatientMedicalProcedureDetail.DetailType must use the value Based On
partOf.referencePatientMedicalProcedureDetailDetailRecordIdFor procedure.partOf information, PatientMedicalProcedureDetail.DetailType must use the value Part Of
statusPatientMedicalProcedureStatusWhile FHIR defines procedure.status as a code set bundle, the Salesforce implementation of PatientMedicalProcedure.Status is picklist.
statusReason.coding.codePatientMedicalProcedureStatusReasonCodeId
category.coding.codePatientMedicalProcedureTypeId
code.coding.codePatientMedicalProcedureCodeId
subject.referencePatientMedicalProcedurePatientIdThe Salesforce implementation of procedure.subject doesn’t support references to groups.
encounterPatientMedicalProcedureClinicalEncounterId
performed.performedDateTimePatientMedicalProcedureStartDatePatientMedicalProcedure.StartDate is used for both procedure.performed.performedDateTime and procedure.performed.performedPeriod. For the latter, the field is used to represent the start date of the period.
recorderPatientMedicalProcedureRecordCreatorId
asserterPatientMedicalProcedureAssertionSourceId
performerCarePerformerThe performer information for a Procedure is represented as CarePerformer records that reference the PatientMedicalProcedure record using their CarePerformer.ParentRecordId field.
performer.function.coding.codeCarePerformerRoleId
performer.actorCarePerformerPersonIdThe Salesforce implementation doesn’t support references to devices.
performer.onBehalfOfCarePerformerAffiliatedOrganizationId
locationPatientMedicalProcedureFacilityId
reasonCodePatientMedicalProcedure
reasonCode.coding.codePatientMedicalProcedureReasonCodeIdWhile FHIR defines procedure.reasonCode as a zero-to-many resource, the Salesforce implementation is zero-to-one
reasonReferencePatientMedicalProcedureReasonReferenceIdWhile FHIR defines procedure.reasonCode as a zero-to-many resource, the Salesforce implementation is zero-to-one. The Salesforce implementation doesn’t support document reference records.
bodySitePatientMedicalProcedureDetailThe body site information of a procedure is represented as PatientMedicalProcedureDetail records that reference the PatientMedicalProcedure record using their PatientMedicalProcedureDetail.PatientMedicalProcedureId field.
bodySite.coding.codePatientMedicalProcedureDetailDetailCodeIdFor procedure.bodySite information, PatientMedicalProcedureDetail.DetailCodeId must reference aCodeSet or CodeSetBundle record.
outcome.coding.codePatientMedicalProcedureOutcomeWhile FHIR defines procedure.outcome as a code, the Salesforce implementation of PatientMedicalProcedure.Outcome is a picklist
reportPatientMedicalProcedureReportIdWhile FHIR defines procedure.report as a zero-to-many resource, the Salesforce implementation is zero-to-one. The Salesforce implementation of procedure.report doesn’t support references to composition or document reference records.
complication.coding.codePatientMedicalProcedureDetailDetailRecordIdFor procedure.complication information, PatientMedicalProcedureDetail.DetailCodeId must reference aCodeSet or CodeSetBundle record.
complicationDetailPatientMedicalProcedureDetailRecordIdFor procedure.complicationDetail information, PatientMedicalProcedureDetail.DetailRecordId must reference a HealthCondition record.
followUpPatientMedicalProcedureDetailThe follow up information of a procedure is represented as PatientMedicalProcedureDetail records that reference the PatientMedicalProcedure record using their PatientMedicalProcedureDetail.PatientMedicalProcedureId field.
followUp.coding.codePatientMedicalProcedureDetailDetailCodeIdFor procedure.followUp information, PatientMedicalProcedureDetail.DetailCodeId must reference aCodeSet or CodeSetBundle record.

Reviews

TypeTemplate
OrganizationMulesoft
Published by
MuleSoft Organization
Published onDec 14, 2022
Asset overview

Asset versions for 1.0.x

Asset versions
VersionActions
1.0.5